Release 10.1A: OpenEdge Development:
Messaging and ESB

Creating a session procedure and connecting to a SonicMQ Broker

The following general steps outline how a 4GL application connects to a SonicMQ Broker for a Pub/Sub session:

The application runs jms/jmssession.p or jms/pubsubsession.p persistently to instantiate the appropriate Session object.
The application sets connection parameters for SonicMQ.
The application calls the beginSession procedure to connect to the OpenEdge Adapter for SonicMQ and the SonicMQ Broker and starts the JMS session.
The application uses the handle of the Session object to create and publish messages to topics and to subscribe to and receive messages from topics.
The application calls the deleteSession procedure in the Session object to close the session and the underlying connection.